OpenEdge Development:<br />Internationalizing Applications Files in the DLC/prolang directory

The DLC/prolang directory contains files that support internationalization and localization of applications. These files reside in subdirectories named for a particular language or locale. For example, DLC/prolang/rus contains files for Russian and DLC/prolang/tai contains files for Thai. For more information on the subdirectories and their contents, see the DLC/prolang/readme file.

Table A–1 describes the files in the DLC/prolang directory. In the table, lng represents a three-letter abbreviation for a particular locale.

Table A–1: Files in DLC/prolang
File	Description
`lng/_tran.df` `lng/code-page.df`	Defines the collation order for the respective language. For languages with multi-byte character sets, the collation order sorts all single-byte characters first. For example, the collation order for Japanese sorts English letters, then half-width Katakana characters, followed by multi-byte characters.
`lng/empty.db`	An empty database labelled with the appropriate code-page and collation table for the language. Copy this database to create your own database.
`lng/language.pf`	Contains typical startup parameters for a particular locale. That is, it sets the collation table and case table commonly used in a locale. Some `lng` subdirectories contain multiple parameter files because some locales that share a language use different code-pages, collation orders, or date formats.
`lng/promsgs.lng`	Contains OpenEdge error messages for a particular locale. Set the `PROMSGS` environment variable to the appropriate file. For example, `PROMSGS=%DLC%\prolang\sch\promsgs.sch`causes an application to display OpenEdge error messages in Simplified Chinese.